This appendix contains messages that can be received from the NDIS device driver. These messages can come from DOS and OS/2 message files. The messages are either displayed or logged to a file.
The term Port nnnnnnnn appears in several messages.
It is used to identify the adapter's instance and bears no
relationship to the physical slots in the computer. If this is the only
adapter, the number will be 00000000.
| LA10001 | IBM PCI Token-Ring Adapter, Version xx
Explanation: Information only. User Action: None. |
| LA10002 | The IBM PCI Token-Ring Adapter UAA (BIA) is xx.
Explanation: Information only. User Action: None. |
| LA10003 | The IBM PCI Token-Ring Adapter is using an LAA of xx.
Explanation: Information only. User Action: None. |
| LA10004 | Revision level xx of the adapter is incompatible
with this driver version.
Explanation: The Revision ID of the adapter is not one that is supported by this version of the device driver. This correlation is enforced to ensure an appropriate match between the hardware and the device driver software. User Action: Contact your support personnel for assistance. You might need to upgrade your adapter, use a different version of the device driver, or do both. |
| LA10005 | A device driver initialization error occurred (failure code
xx).
Explanation: An unexpected error occurred during initialization of the device driver. User Action: Shut down the computer correctly and switch OFF the power to the machine. Restart the computer by switching it ON again. If the error persists, contact your support personnel. |
| LA10006 | The configuration parameter xx was specified
incorrectly. Its default value will be used.
Explanation: The value of a configuration parameter was incorrectly specified. User Action: Edit the configuration file (or rerun the configuration program) to specify the correct value within the allowed range. Check the adapter installation instructions for additional information. |
| LA10007 | The configuration parameter values have forced the internal data
blocks to exceed the allowed limit.
Explanation: The combination of configuration parameters being used requires more than the 64-KB memory area that is available for this adapter instance to hold its internal control information. User Action: Lower the value of the MaxTransmits or MinRcvBuffs parameters from their current setting to reduce the amount of control block storage required by the device driver. Shut down and restart the computer to activate this configuration change. |
| LA10008 | Unable to register interrupt level xx for
this adapter.
Explanation: The hardware interrupt level assigned to this adapter was not able to be registered (hooked) by the device driver. User Action: Check the configuration of your computer, looking for other devices that are assigned the same interrupt level as this adapter. Try removing the conflicting device from the machine and restarting the computer to see if the problem is resolved. If so, determine whether the conflicting device can be left out of the machine, or whether the machine can be reconfigured to resolve the conflict. Note that in most PCI machines, the PCI BIOS assigns certain system resources to the devices found in the computer, including the interrupt level. |
| LA10010 | A hardware failure occurred while attempting to open the adapter.
Explanation: A hardware error was detected when opening the adapter for network operation. User Action: Run the diagnostics program to isolate the problem, and contact your support personnel. If no problem was identified by the diagnostics, check that the cable is attached securely to both the adapter and the network interface (wall plate). Switch the computer OFF and then ON again to restart the machine. If the problem persists, contact your support personnel. |
| LA10011 | A possible lobe wire failure was detected while attempting to insert
into the network.
Explanation: The adapter is not correctly connected to the token-ring network. User Action: Check that the cable is securely attached to both the adapter and to the token-ring network. You might need to contact your local network administrator to ensure that the cabling in the building is intact and that the network concentrator to which you are attached is operational. If the error persists, try using a different cable. |
| LA10012 | A signal loss condition was detected while attempting to insert into
the network.
Explanation: The token-ring network is not functioning correctly. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time. |
| LA10013 | The lobe wire connected to the adapter is not attached to the
network.
Explanation: The adapter is not correctly connected to the token-ring network. User Action: Check that the cable is securely attached to both the adapter and to the token-ring network. You might need to contact your local administrator to ensure that the cabling in the building is intact and that the network concentrator to which you are attached is operational. If the error persists, try using a different cable. |
| LA10014 | The configured data rate for the adapter does not match that of the
network.
Explanation: The operational speed of the token-ring network does not match the configured speed of the adapter. User Action: Change the setting of the DataRate configuration parameter to match the speed of the network to which the adapter is attached. Your local network administrator should be able to tell you which speed to use. Setting the DataRate parameter value to Auto will allow the adapter to automatically determine the correct speed setting to use when connecting to the network, provided that this is not the only adapter active on the Token Ring. This message is relevant for 4-Mbps or 16-Mbps operation only. Consult the adapter installation instructions for additional information on setting the DataRate parameter. |
| LA10015 | An adapter timeout occurred while attempting to insert into the
network.
Explanation: The token-ring network is not functioning correctly. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time. |
| LA10016 | A ring failure condition was detected while attempting to insert
into the network.
Explanation: The token-ring network is not functioning correctly. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time. |
| LA10017 | A ring beaconing condition was detected while attempting to insert
into the network.
Explanation: The token-ring network is not functioning correctly. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time. |
| LA10018 | A duplicate network address was detected while attempting to insert
into the network.
Explanation: The address specified for the NetAddress configuration parameter is being used by another adapter (or ring station) on the network. User Action: Modify the configuration file to change the NetAddress parameter value being used for this adapter, or remove the NetAddress parameter to allow the adapter's universally administered address to be used. Contact your local network administrator for assistance with choosing a new NetAddress parameter value, or with having the conflicting adapter removed from the same token-ring network as this adapter. |
| LA10019 | A ring parameter failure occurred while attempting to insert into
the network.
Explanation: The token-ring network is not functioning correctly. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time. |
| LA10020 | The adapter was forced to remove itself while attempting to insert
into the network.
Explanation: The token-ring network rejected the attempt by this adapter to connect to it. User Action: Contact your local network administrator to determine the status of your network, or try connecting again at a later time. |
| LA10021 | A hardware failure occurred while attempting to open the adapter.
Explanation: A hardware error was detected when opening the adapter for network operation. User Action: Run the diagnostics program to isolate the problem, and contact your support personnel. If no problem was identified by the diagnostics, check that the cable is attached securely to both the adapter and the network interface (wall plate). Switch the computer OFF and then ON again to restart the machine. If the problem persists, contact your support personnel. |
| LA10022 | A hardware failure occurred while attempting to open the adapter.
Explanation: A hardware error was detected when opening the adapter for network operation. User Action: Run the diagnostics program to isolate the problem and contact your support personnel. If no problem was identified by the diagnostics, check that the cable is attached securely to both the adapter and the network interface (wall plate). Switch the computer OFF and then ON again to restart the machine. If the problem persists, contact your support personnel. |
| LA10023 | The adapter cannot be opened in AutoSense mode if it is the only
active station on the network.
Explanation: The adapter DataRate configuration parameter is set to Auto (which is also the default value if the parameter is not specified), but the adapter is the first station to open on the token-ring network. User Action: This adapter is designed to not open onto the attached token-ring network if it is configured to use AutoSense detection and if it would have been the first active ring station. The possible remedies are to try to connect again at a later time when at least one other ring station is active on the network (such as a network server), or to change the configuration value so that the DataRate parameter is set to a specific ring-speed value of M16 or M4 and restart the computer. Note that setting a specific value of M16 or M4 for the DataRate parameter will cause this adapter to establish the operational speed of the token-ring network if it is still the first active ring station. This message is relevant for 4-Mbps or 16-Mbps operation only. Check the adapter installation instructions for additional information on setting the DataRate parameter. |
| LA10024 | The adapter attempted to perform a Remote Program Load but failed
monitor contention.
Explanation: The adapter was opened as a Remote Program Load (RPL) client, but was unable to locate an RPL server on the network. User Action: Make sure that there is an active Remote Program Load server on the network and that it is configured to recognize this adapter's address. |
| LA10025 | A network protocol error occurred while attempting to operate the
adapter in full duplex mode.
Explanation: The adapter was unable to successfully communicate with a token-ring switch when attempting to open for full-duplex operation. User Action: Check that your full-duplex switch is functioning correctly and that the adapter is correctly connected to it. If this problem persists, contact your support personnel. |
| LA10026 | Unable to automatically change to xx Mbps
operation. Please reboot the computer.
Explanation: The adapter attempted to open at one speed, but found the Token Ring operating at another speed. The configuration parameters used during initialization processing, notably the maximum frame size, preclude reliable operation at the new speed, so all additional attempts to open the adapter will be rejected. Rebooting the computer allows the new speed to be factored into the initialization processing without requiring a configuration change in most cases. User Action: Shut down and restart the computer. Normally, no explicit configuration changes are required to begin operating at the current operational speed of the Token Ring. Optionally, you might be able to change the value of the configuration parameter that specifies the maximum frame size to a value of 4500 or less to eliminate the need to reboot the computer for a similar situation in the future. |
| LA10027 | The adapter opened for token ring, xx Mbps.,
half duplex.
Explanation: Information only. User Action: None. |
| LA10028 | The adapter opened for token ring, xx Mbps.,
full duplex.
Explanation: Information only. User Action: None. |
| LA10033 | Adapter analysis code is xx.
Explanation: Information only. User Action: None. |
| LA10034 | Adapter full-duplex operation has now been activated.
Explanation: Information only. User Action: None. |
| LA10042 | A device driver initialization error occurred (failure code
xx).
Explanation: An unexpected error occurred during initialization of the device driver. User Action: Shut down the computer and switch OFF the power to the machine. Restart the computer by switching it ON again. If the error persists, contact your support personnel. |
| LA10043 | No adapter instances recognized by this device driver were found
in PROTOCOL.INI.
Explanation: The PROTOCOL.INI file does not have a section defined by the correct DRIVERNAME= line anywhere within it. User Action: If you intend to run this device driver, make sure to define a valid network configuration in the PROTOCOL.INI file. If you do not intend to run this device driver, remove its DEVICE= statement from the CONFIG.SYS file. |
| LA10044 | The NDIS 2.0 Protocol Manager could not be opened.
Explanation: An unexpected error occurred when the program attempted to open the Protocol Manager. User Action: Check the drive and directory to ensure that the Protocol Manager is located in the path specified in the CONFIG.SYS file. If this error persists, consider reinstalling the NDIS 2.0 network support software. |
| LA10045 | Could not find the PROTOCOL.INI file image.
Explanation: An unexpected error occurred when the program attempted to read the PROTOCOL.INI file image through interaction with the Protocol Manager. User Action: Check the drive and directory to ensure that the Protocol Manager is located in the path specified in the CONFIG.SYS file. Verify that a valid PROTOCOL.INI file exists in the proper location. If this error persists, consider reinstalling the NDIS 2.0 network support software. |
| LA10046 | The required DRIVERNAME parameter was not found in
PROTOCOL.INI.
Explanation: The parameter specifying the driver name (DRIVERNAME) was not found in the PROTOCOL.INI file. This parameter is required. User Action: Change PROTOCOL.INI to specify the proper information. |
| LA10047 | The NetAddress value in PROTOCOL.INI is invalid and will be
ignored.
Explanation: The value specified for the network address parameter in PROTOCOL.INI is not valid for one of the following reasons:
User Action: Remove or correct the NetAddress configuration parameter value. A valid value for this parameter is 12 characters long and must be enclosed in double quotation marks. For token-ring adapters, the locally administered address must be within the hex range 400000000000 to 7FFFFFFFFFFF. Make sure not to set the corresponding group address bit, which is the high-order bit in token-ring addressing notation. |
| LA10048 | An unrecognized parameter xx was found in
PROTOCOL.INI.
Explanation: An unrecognized parameter was found while processing a section of the PROTOCOL.INI file defined for this device driver. User Action: Correct the parameter name or remove it from PROTOCOL.INI. Refer to the installation manual that came with your adapter for more information on the configuration parameters. |
| LA10049 | The configuration parameter xx was specified
incorrectly. Its default value will be used.
Explanation: An invalid value was specified for a configuration parameter in the PROTOCOL.INI file. A default value has been substituted. User Action: Change the PROTOCOL.INI file to specify a valid value for the configuration parameter that is in error. Refer to the installation manual that came with the adapter for more information on the allowable settings for this particular parameter. The device driver has proceeded with its initialization using a predetermined default value for this parameter. |
| LA10050 | The NDIS 2.0 device driver was not able to register with the
Protocol
Manager.
Explanation: An unexpected error occurred when the program attempted to register a adapter with the Protocol Manager. User Action: Check the drive and directory to ensure that the Protocol Manager is located in the path specified in the CONFIG.SYS file. If this error persists, consider reinstalling the NDIS 2.0 network support software. |
| LA10051 | The configuration parameter values have forced the internal data
blocks to exceed the allowed limit.
Explanation: The combination of configuration parameters being used requires more than the 64-KB memory area that is available for this adapter instance to hold its internal control information. User Action: Lower the value of the MaxTransmits or MinRcvBuffs parameters in the PROTOCOL.INI file to reduce the amount of control block storage required by the device driver. Shut down and restart the computer to activate this configuration change. |
| LA10053E (DOS Only) | Device Driver could not initialize. Failure code:
xx
Explanation: The device driver was not able to initialize itself. This is most often caused by conflicts between the device driver and other resources in the system. User Action: Record this message number and the failure code and contact your support personnel for assistance. |
| LA10054E (DOS Only) | No adapters supported by %1 were found or adapters were not
correctly configured by the machine and its BIOS.
Explanation: The device driver was not able to find any adapters that it knows about. Either the adapter is not installed in the computer, the adapter is malfunctioning, or the system BIOS has not correctly configured the adapter. User Action: Record this message number and contact your support personnel for assistance. |
| LA10055E (DOS Only) | No adapters initialized correctly. xx adapters
were found in the machine.
Explanation: The device driver was able to find the stated number of adapters. However, none of the adapters were successfully initialized. This message is often displayed along with one or more other messages from the device driver. User Action: Record this message number as well as any other messages from the device drivers along with any specific failure codes in the messages and contact your support personnel for assistance. |